-
Notifications
You must be signed in to change notification settings - Fork 2
implement cluster_report_destination_override #93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| def monitor_cluster( | ||
| cluster_id: str, | ||
| polling_period: int = 20, | ||
| cluster_report_destination_override: dict = None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it better to type the None as Optional too?
| cluster_report_destination_override: dict = None, | |
| cluster_report_destination_override: Optional[dict] = None, |
| sleep(polling_period) | ||
|
|
||
|
|
||
| def _define_write_file(file_key, filesystem, bucket): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice moving logic into sub-functions!
romainissynced
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
metal
|
Not going to merge quite yet, id like to revalidate my tests - i missed the hardcoded line in the reporting job that uses latest library |
|
worked on the sandbox environment for both monitor cluter and the record run job |
Summary
please add a few lines to give the reviewer context on the changes
Relevant Design Doc
Adding the option to pass in a dict of
filesystemandbase_prefixto allow overriding of the logging location for cluster monitoringChecklist
Before formally opening this PR, please adhere to the following standards:
Related Jira Ticket
Add any relevant testing examples or screenshots.
Will test existing functionality remains.
validated retention of existing functionality by pointing our sandbox environment's init script to this branch. Ran with the logging location both to dbfs and s3.


DBFS:
s3:
pulled both files down and validated they populated properly.